home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19980424-19980901
/
000173_news@newsmaster….columbia.edu _Tue Jun 2 05:53:41 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
4KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id FAA07770
for <kermit.misc@watsun.cc.columbia.edu>; Tue, 2 Jun 1998 05:53:40 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id FAA00667
for kermit.misc@watsun; Tue, 2 Jun 1998 05:53:40 -0400 (EDT)
Path: news.columbia.edu!newsfeed.nyu.edu!news.idt.net!news-peer-east.sprintlink.net!news-peer.sprintlink.net!news-backup-east.sprintlink.net!news.sprintlink.net!209.90.0.8!alpha.sky.net!newshub.cts.com!newshub.nosc.mil!dog.ee.lbl.gov!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Kermit for DOS Lockup Problems
Message-ID: <ded0vT5Q2vdD@cc.usu.edu>
Date: 1 Jun 98 21:45:27 MDT
References: <3572C5AA.EDB12434@inxpress.net>
Organization: Utah State University
Lines: 46
Xref: news.columbia.edu comp.protocols.kermit.misc:8842
In article <3572C5AA.EDB12434@inxpress.net>, Bob Hartung <bhartung@inxpress.net> writes:
> HELP!
>
> I am trying to use Kermit version 3 with the MSK315 patch on DOS PC's on
> a Novell 4.11 ethernet LAN running Novell's VLM 1.21 clients. We also
> use Novell's DHCP to allocate addresses.
>
> We want to use Kermit to telnet to an RS/6000 AIX unix host on the same
> LAN. We have been using Novell's LAN WorkGroup for DOS but we need to
> retire it.
>
> I have been getting numerous and repeated complaints of lockups on
> several of the PC's using Kermit. By lockup, my users actually mean that
> they experience both PC lockup (system won't respond to any input and
> needs rebooting) to loosing the connection to the RS/6000 and ending up
> at the "Kermit" prompt.
>
> I am relying on Kermit to provide TCP/IP connectivity via the Novell ODI
> driver. Is there some kind of setting in either the MSCUSTOM.INI or
> MSKERMIT.INI files that need to be set in order to maintain a connection
> to a local host?
----------
I can say confidently, it's not Kermit. That leaves just about
everything else to consider, oh joy. Start with the lan adapter, and its
settings. If it is a "parallel tasking" device then please use one that
isn't; they have designed-in difficulties. Look at your lan to see if
broadcast traffic is well out of control, and if there are stations using
the IP address of a Kermit client. And at switches, which if in full duplex
mode will drop frames like crazy in the fast to slow direction. And if you
are using shim ODIPKT then remove it because MSK is a native ODI speaker.
Interrupt (IRQ) conflicts are fatal, so eliminate that possibility too.
TSRs that hog the machine are also fatal, the first and most infamous
being plain old DOS PRINT; they don't release the system so that other
components can respond to real time events. Finally the short list includes
not running another TCP/IP stack on the machine at the same time; that's
fratracide.
We hope you are not running MSK in a Windows DOS box without
shims ODIPKT plus WINPKT. That's a mandatory combination for the DOS box
environment.
VLM 1.21 is normally just fine. There can be memory management
troubles, of course, and flakey memory itself, but those normally afflict
the IPX side of the house and not Kermit's TCP/IP (the ODI drivers are
not loaded above 1MB, but VLMs are).
Beyond this standard advice we would need more detail about the
systems, after you do fine tooth combing of them.
Joe D.